Well there is still a small bug somewhere between small and big width sizes (right when the navigation disappears) where stuff is drawn "outside" the browser without being able to scroll there.

But it's much better thanks! Would this be solved by using prism everywhere? Or should we change the generated dom somehow? (No need to do it but if I ever find the time I might change it)

Well there is still a small bug somewhere between small and big width sizes (right when the navigation disappears) where stuff is drawn "outside" the browser without being able to scroll there.

But it's much better thanks! Would this be solved by using prism everywhere? Or should we change the generated dom somehow? (No need to do it but if I ever find the time I might change it)

@matthid Changing it to prism would be a step in the right direction, because then we can specify the whole layout in the api docs and avoid using tables (which is now predefined by FSFormatting).

@florianbader But you mean only the tables for the code-blocks, correct? afaik the other tables are defined in the template

@florianbader But you mean only the tables for the code-blocks, correct? afaik the other tables are defined in the template

@matthid Correct. The bug occurs if you have a pre-tag inside a table, so removing one layer of table inside the template isn't enough, you would need to remove the table in the code-blocks and also the table in the api docs.